Aight I got there 👍 Full upgrade from Remix v1 -> v2 -> React Router v7 (which ended up breaking linting, so that's now on eslint v9 too)

Whoops bot doesn't actually run, just the webapp

Rebased to collapse some "oops"-tier commits. This is actually like 3x migrations in 1 PR which makes me a bit nervous, but I've validated about as much as I can locally. Caught a few snafus, fingers crossed there aren't any weirder ones — this does a lot to change the entrypoints and adds a new prod/dev check in order to enable hot reload functionality, so it's pretty high risk. Will be monitoring and validate the deploy once it lands

Welp this doesn't actually do a correct production build, it's missing the outside server.js function that actually starts the bot + http server. This is a pretty fragile and complicated setup unfortunately to get working:

• react-router has a cli that does a build. The "framework mode" is actually a pretty complicated mix of bundler plugins, typegen, build CLI, dev server… it turns it guts inside out so at least I'm not monkeypatching anything, but it means I have to understand how it's glued together.
• The template here basically punts on the issue of integrating into the build by introducing an entirely-separate server.js script that doesn't go through any other part of the build process. This does not work here, because I have more than just an express server, and the server script relies on TS configuration to appropriately run.
• This runs in dev currently by executing tsx app/index.ts, but tsx doesn't work for compiling a production build. tsc -b either duplicates work done by react-router build, or produces an incomplete/non-functional output. Because the folder structure isn't preserved between dev/prod, it seems confusing to set up a single script that exists in 2 different contexts.

I think I can move the code around such that there's a dev/prod script that starts up the server appropriately, but it's diverging a good bit from the template. Since this asks for a plain-JS startup script, I'm going to see if I can get that working with minimal fuss, without making it too difficult to understand and change.